Distances between Requirements Engineering and Later Software Development Activities: A Systematic Map

[Context and Motivation] The main role of requirements engineering (RE) is to guide development projects towards implementing products that will appeal to customers. To effectively achieve this RE needs to be coordinated with and clearly communicated to the later software development activities. [Question/Problem] Communication gaps between RE and other development activities reduce coordination and alignment, and can lead to project delays and failure to meet customer needs. [Principle ideas/results] The main hypothesis is that coordination is enhanced by proximity to RE roles and artefacts, and that distances to later activities increase the effort needed to align requirements with other development work. Thirteen RE-related distances have been identified through a systematic map of existing research. [Contribution] Reported distances are mapped according to research type, RE activity and later software development activities. The results provide an overview of RE distances and can be used a basis for defining a theoretical framework.